User interfaces for widgets

ABSTRACT

Techniques for displaying widgets are described. In some examples, concurrently displaying, via the display device, a wake screen of the electronic device that includes one or more notifications and a first set of one or more user interface elements. While concurrently displaying the wake screen and the first set of one or more user interface elements, detecting a first user input; and in response to detecting the first user input: if the first user input includes movement in a first direction, ceasing to display the first set of one or more user interface elements and displaying the one or more notifications; and in accordance with a determination that the first user input includes selection of a user interface element of the first set of one or more user interface elements and the electronic device is in an unlocked state, displaying an application user interface corresponding to the selected user interface element.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Nonprovisional PatentApplication Ser. No. 16/737,372, titled “USER INTERFACES FOR WIDGETS,”filed Jan. 8, 2020, which claims priority to U.S. Provisional PatentApplication Ser. No. 62/843,507, titled “USER INTERFACES FOR WIDGETS,”filed May 5, 2019, the entire contents of which are hereby incorporatedby reference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for displaying widgets.

BACKGROUND

An electronic device can have applications installed on the device,where the applications enable access to certain functions andapplication data. Techniques are implemented on the electronic devicefor displaying application data.

BRIEF SUMMARY

Some techniques for displaying application data using electronicdevices, however, are generally cumbersome and inefficient. For example,some existing techniques use a complex and time-consuming userinterface, which may include multiple key presses or keystrokes.Existing techniques require more time than necessary, wasting user timeand device energy. This latter consideration is particularly importantin battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for displaying applicationdata using widgets. Such methods and interfaces optionally complement orreplace other methods for displaying application data. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

In some embodiments, a method is described. The method comprises: at anelectronic device with a display device: displaying, via the displaydevice, a first plurality of application icons without displaying afirst set of one or more user interface elements, wherein theapplication icons are selectable to display application user interfacesfor corresponding applications; while displaying, via the displaydevice, the first plurality of application icons, detecting a first userinput; and in response to detecting the first user input: in accordancewith a determination that the first user input includes movement in afirst direction: ceasing display of the first plurality of applicationicons; and displaying, via the display device, a second plurality ofapplication icons that are different from the first plurality ofapplication icons, wherein the application icons are selectable todisplay application user interfaces for corresponding applications; andin accordance with a determination that the first user input includesmovement in a second direction that is different from the firstdirection: modifying display of the first plurality of application iconsto change a distance between a first application icon of the firstplurality of application icons and a second application icon of thefirst plurality of application icons; and concurrently displaying, viathe display device, the modified first plurality of application iconsand the first set of one or more user interface elements.

In some embodiments, a non-transitory computer-readable storage mediumis described. The non-transitory computer-readable storage medium storesone or more programs configured to be executed by one or more processorsof an electronic device with a display device, the one or more programsincluding instructions for: displaying, via the display device, a firstplurality of application icons without displaying a first set of one ormore user interface elements, wherein the application icons areselectable to display application user interfaces for correspondingapplications; while displaying, via the display device, the firstplurality of application icons, detecting a first user input; and inresponse to detecting the first user input: in accordance with adetermination that the first user input includes movement in a firstdirection: ceasing display of the first plurality of application icons;and displaying, via the display device, a second plurality ofapplication icons that are different from the first plurality ofapplication icons, wherein the application icons are selectable todisplay application user interfaces for corresponding applications; andin accordance with a determination that the first user input includesmovement in a second direction that is different from the firstdirection: modifying display of the first plurality of application iconsto change a distance between a first application icon of the firstplurality of application icons and a second application icon of thefirst plurality of application icons; and concurrently displaying, viathe display device, the modified first plurality of application iconsand the first set of one or more user interface elements.

In some embodiments, a transitory computer-readable storage medium isdescribed. The transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: displaying, via the display device, a firstplurality of application icons without displaying a first set of one ormore user interface elements, wherein the application icons areselectable to display application user interfaces for correspondingapplications; while displaying, via the display device, the firstplurality of application icons, detecting a first user input; and inresponse to detecting the first user input: in accordance with adetermination that the first user input includes movement in a firstdirection: ceasing display of the first plurality of application icons;and displaying, via the display device, a second plurality ofapplication icons that are different from the first plurality ofapplication icons, wherein the application icons are selectable todisplay application user interfaces for corresponding applications; andin accordance with a determination that the first user input includesmovement in a second direction that is different from the firstdirection: modifying display of the first plurality of application iconsto change a distance between a first application icon of the firstplurality of application icons and a second application icon of thefirst plurality of application icons; and concurrently displaying, viathe display device, the modified first plurality of application iconsand the first set of one or more user interface elements.

In some embodiments, an electronic device is described. The electronicdevice comprises: a display device; one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:displaying, via the display device, a first plurality of applicationicons without displaying a first set of one or more user interfaceelements, wherein the application icons are selectable to displayapplication user interfaces for corresponding applications; whiledisplaying, via the display device, the first plurality of applicationicons, detecting a first user input; and in response to detecting thefirst user input: in accordance with a determination that the first userinput includes movement in a first direction: ceasing display of thefirst plurality of application icons; and displaying, via the displaydevice, a second plurality of application icons that are different fromthe first plurality of application icons, wherein the application iconsare selectable to display application user interfaces for correspondingapplications; and in accordance with a determination that the first userinput includes movement in a second direction that is different from thefirst direction: modifying display of the first plurality of applicationicons to change a distance between a first application icon of the firstplurality of application icons and a second application icon of thefirst plurality of application icons; and concurrently displaying, viathe display device, the modified first plurality of application iconsand the first set of one or more user interface elements.

In some embodiments, an electronic device is described. The electronicdevice comprises: a display device; means for displaying, via thedisplay device, a first plurality of application icons withoutdisplaying a first set of one or more user interface elements, whereinthe application icons are selectable to display application userinterfaces for corresponding applications; means, while displaying, viathe display device, the first plurality of application icons, fordetecting a first user input; and means, in response to detecting thefirst user input: in accordance with a determination that the first userinput includes movement in a first direction: for ceasing display of thefirst plurality of application icons; and for displaying, via thedisplay device, a second plurality of application icons that aredifferent from the first plurality of application icons, wherein theapplication icons are selectable to display application user interfacesfor corresponding applications; and in accordance with a determinationthat the first user input includes movement in a second direction thatis different from the first direction: for modifying display of thefirst plurality of application icons to change a distance between afirst application icon of the first plurality of application icons and asecond application icon of the first plurality of application icons; andfor concurrently displaying, via the display device, the modified firstplurality of application icons and the first set of one or more userinterface elements.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for displaying widgets, thereby increasing the effectiveness,efficiency, and user satisfaction with such devices. Such methods andinterfaces may complement or replace other methods for displayingwidgets.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6AC illustrate exemplary user interfaces for displaying widgetsin accordance with some embodiments.

FIGS. 7A-7B are a flow diagram illustrating a method for displayingwidgets in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for displaying widgets. For example, a user may find itdifficult to easily access certain application data. The user may usewidgets to access the application data, but it may be difficult tonavigate to the widgets. Additionally, the user may not be able toaccess other desired functions of the device while widgets are beingdisplayed. Accordingly, techniques are needed for displaying widgets inreadily accessible manner. Moreover, techniques are needed that allowthe user to perform a variety of functions while having access to theapplication data provided by the widgets. Such techniques can reduce thecognitive burden on a user who accesses application data via widgets,thereby enhancing productivity. Further, such techniques can reduceprocessor and battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for displaying widgets.FIGS. 6A-6AC illustrate exemplary user interfaces for display widgets.FIGS. 7A-7B are a flow diagram illustrating methods of displayingwidgets in accordance with some embodiments. The user interfaces inFIGS. 6A-6AC are used to illustrate the processes described below,including the processes in FIGS. 7A-7B.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch screen displays and/or touchpads),are, optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2 ) optionally include an up/downbutton for volume control of speaker 111 and/or microphone 113. The oneor more buttons optionally include a push button (e.g., 206, FIG. 2 ).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. patents: U.S. Pat. No. 6,323,846 (Westerman etal.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No.6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1,each of which is hereby incorporated by reference in its entirety.However, touch screen 112 displays visual output from device 100,whereas touch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including method 700 (FIGS.7A-7B). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-where the representations 578A-578C appear and moveupwards as the intensity of contact 562 increases toward the deep pressintensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UP”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6AC illustrate exemplary user interfaces for widgets, inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses in FIGS. 7A-7B.

FIG. 6A depicts electronic device 600, which is a tablet computer withdisplay 602, hardware button 604, and biometric sensor 606. In someembodiments, electronic device 600 is, or includes one or more featuresof, electronic device 100, 300, or 500.

At FIG. 6A, electronic device 600 displays home screen 608 while thedevice in an unlocked state and in a landscape orientation. Theelectronic device detects that the device is in the landscapeorientation and provides the user interfaces for a landscape view. Insome embodiments, a home screen is a displayed user interface thatserves as a starting point for navigating the contents and functions ofa device. As the user explores the home screen, the home screen can bemodified to include new user interface objects (e.g., application icons,widgets) or modified to remove existing user interface objects.

In FIG. 6A, home screen 608 includes a first page of application (app)icons and dock region 610. The first page of app icons includes appicons 612A-612Z organized in a grid layout of rows and columns. Dockregion 610 includes app icons 614A-614F organized in a single row.Immediately above dock region 610, electronic device 600 displays pageindicator 616. Page indicator 616 provides an indication of the numberof pages that exist, and also which page in the sequence of pages iscurrently being displayed.

As depicted in FIG. 6A, page indicator 616 includes three dots in a row,with the second dot filled in. This provides an indication that threepages exist, and that the second page in the sequence of pages iscurrently being displayed. As a result, page indicator 616 also providesan indication that pages exist to the left and right of the currentlydisplayed page (e.g., the first page of app icons). In some embodiments,the contents of the page to the left is accessible via a left-to-rightswipe gesture, while the contents of the page to the right is accessiblevia a right-to-left swipe gesture. As further described below, the pageto the left is a page of widget(s), and the page to the right is asecond page of app icons.

At FIG. 6A, electronic device 600 displays app icons 612A-612Z that,when selected, result in launching (or displaying) an applicationcorresponding to the selected app icon. By launching the application, auser can access content from that application. However, suppose a userwishes to instead access content from an application via a widget. Adisplayed widget typically includes information from an application. Theinformation is usually useful while being glanceable. To access thewidget, the user performs a swipe gesture (e.g., swipe 618) withmovement in the left-to-right direction on display 602.

As a result, while in a landscape orientation and while displaying appicons 612A-612Z, electronic device 600 detects swipe gesture 618 in aregion corresponding to (e.g., occupied by) app icons 612A-612Z. In someembodiments, the region corresponding to app icons 612A-612Z does notinclude dock region 610 and/or the region occupied by status bar 620.

In some embodiments, upon detecting swipe gesture 618, electronic device600 determines the direction of the movement in swipe gesture 618. Asdepicted in FIG. 6B-6C, upon determining that the direction of themovement in swipe gesture 618 is left-to-right, electronic device 600modifies the display of home screen 608 by merging the page of widget(s)onto home screen 608.

Merging the page of widget(s) onto home screen 608 includes slidingwidget 622A onto home screen 608 (e.g., from the left side of thedisplay), and resizing the spacing between app icons 612A-612Z in orderto accommodate the display of widget 622A on home screen 608. That is,the horizontal spacing between the app icons uniformly decreases. Forexample, the horizontal spacing between app icon 612A and app icon 612Bdecreases. Similarly, the horizontal spacing between app icon 612C andapp icon 612D decreases by the same amount. In contrast, the verticalspacing between the app icons remains the same.

Moreover, as depicted in FIGS. 6B-6C, upon determining that thedirection of the movement in swipe gesture 618 is left-to-right,electronic device 600 horizontally shifts to the right the location atwhich app icons 612A-612Z are displayed. For example, app icon 612A inFIG. 6C is displayed at a location that is to the right of the locationat which app icon 612A is displayed in FIG. 6A. The reduction inhorizontal spacing of the app icons and the shifting of the app icons tothe right provide additional space on home screen 608 to accommodate thedisplay of widget 622A. While app icons 612A-612Z undergo visual changesas discussed above, app icons 614A-614F in dock region 610 remainunchanged in response to swipe gesture 618. For example, the horizontalspacing between app icon 614A and app icon 614B in dock region 610remains unchanged.

At FIG. 6C, upon determining that the direction of the movement in swipegesture 618 is left-to-right, electronic device 600 concurrentlydisplays widget 622A and app icons 612A-612Z on home screen 608. Widget622A is a calendar widget that shows glanceable information from acalendar application. In some embodiments, widget 622A is of aparticular category known as “pinned”. Other categories can include“favorites” and “library”. In some embodiments, electronic device 600uses the categories to determine which widgets are to be displayed. Forexample, in some embodiments, upon determining that the direction of themovement in swipe gesture 618 is left-to-right, electronic deviceconcurrently displays app icons 612A-612Z and only the “pinned” widgets(e.g., 622A). Thus, in some embodiments, widgets in the “favorites” and“library” categories would not be displayed. Widgets can be reorganizedin the different categories in the edit mode, as further described belowwith respect to FIG. 6P.

As a result of merging the page of widget(s) onto home screen 608,electronic device 600 updates page indicator 616 to reflect that thetotal number of pages has been reduced from three to two. Additionally,as a result of merging the page of widget(s) onto home screen 608, timeindicator 624 and date indicator 626 moves from status bar 620 to widgetregion 628 (further described below).

It is noted that the above described result in FIGS. 6B-6C occurs as aresult of detecting a swipe gesture with movement in the left-to-rightdirection. For the result that occurs due to detecting a swipe gesturewith movement in the right-to-left direction, refer to the descriptionbelow with respect to FIGS. 6Z-6AA.

As discussed above, upon determining that the direction of the movementin swipe gesture 618 is left-to-right, electronic device 600concurrently displays widget 622A and app icons 612A-612Z on home screen608. As depicted in FIG. 6C, electronic device 600 also generates twoadjacent, non-overlapping regions for displaying the widget(s) and appicons. These two regions are widget region 628, a region occupied by(e.g., corresponding to) widget(s), and app region 630, a regionoccupied by (e.g., corresponding to) app icons. Boundary line 632 marksthe boundary between widget region 628 and app region 630. FIG. 6Cdepicts boundary line 632 for illustrative purposes, as electronicdevice 600 does not actually display boundary line 632.

As shown in FIG. 6C, electronic device 600 displays widget(s) (e.g.,622A) in widget region 628, and displays app icons in app region 630.Widget region 628 is adjacent to and does not overlap with app region630. Moreover, in some embodiments, both widget region 628 and appregion 630 do not include dock region 610 and the region occupied bystatus bar 620.

At FIG. 6C, while concurrently displaying widget 622A and app icons612A-612Z, electronic device 600 detects tap gesture 634 at app icon612I. Upon detecting tap gesture 634, electronic device 600 launches acalendar application and replaces display of home screen 608 withdisplay of user interface 636 of the calendar application, as depictedin FIG. 6D. In some embodiments, instead of detecting tap gesture 634,electronic device 600 detects tap gesture 638 at widget icon 640. Widgeticon 640 is a reduced size version of app icon 612I. In someembodiments, upon detecting tap gesture 638, electronic device 600launches a calendar application and replaces display of home screen 608with display of user interface 636 of the calendar application, asdepicted in FIG. 6D. Thus, in some embodiments, detecting a tap gestureat app icon 612I causes the same application to be displayed asdetecting a tap gesture at widget icon 640.

At FIG. 6D, the user performs a swipe gesture to navigate back to homescreen 608. As a result, while displaying user interface 636 of thecalendar application, electronic device 600 detects swipe gesture 642starting near the bottom edge of display 602 with movement in an upwarddirection. Upon detecting swipe gesture 642, electronic device 600replaces display of user interface 636 with display of home screen 608.The previous state of home screen 608 persists despite the interveningdisplay of user interface 636 of the calendar application. Specifically,as shown in FIG. 6E, upon detecting swipe gesture 642, electronic device600 again concurrently displays widget 622A and app icons 612A-612Z onhome screen 608. In some embodiments, instead of concurrently displayingwidget 622A and app icons 612A-612Z upon detecting swipe gesture 642,electronic device 600 returns to the home screen depicted in FIG. 6A.Specifically, electronic device 600 displays app icons 612A-612Z withoutwidget 622A.

At FIG. 6E, the user performs a swipe gesture to navigate to the secondpage of app icons. As a result, while concurrently displaying widget622A and app icons 612A-612Z, electronic device 600 detects swipegesture 644 in app region 630. In some embodiments, upon detecting swipegesture 644 in app region 630, electronic device 600 determines thedirection of the movement in swipe gesture 644. Upon determining thatthe direction of the movement in swipe gesture 644 is right-to-left,electronic device 600 replaces display of the widget(s) and the firstpage of app icons with display of the second page of app icons.Specifically, electronic device 600 replaces display of widget 622A andapp icons 612A-612Z with display of app icons 612AA-612AK, as shown inFIG. 6F. In some embodiments, upon determining that the direction of themovement in swipe gesture 644 is right-to-left, electronic device 600replaces display of app icons 612A-612Z with app icons 612AA-AK, whilemaintaining display of the widget 622A.

It is noted that the above described result in FIG. 6E occurs as aresult of detecting a swipe gesture in app region 630 with movement inthe right-to-left direction, while electronic device 600 concurrentlydisplays widget(s) and the first page of app icons. For the result thatoccurs due to detecting a swipe gesture in app region 630 with movementin the left-to-right direction, refer to the description below withrespect to FIG. 6AC. For the result that occurs due to detecting a swipegesture in widget region 628 with movement in the right-to-leftdirection, refer to the description below with respect to FIGS. 6Y-6Z.

At FIG. 6F, the user performs a swipe gesture to navigate back to thefirst page of app icons. As a result, while concurrently displayingwidget 622A and app icons 612AA-612AK, electronic device 600 detectsswipe gesture 646 in app region 630 with movement in the left-to-rightdirection. Upon detecting swipe gesture 646, electronic device 600replaces the second page of app icons with the first page of app icons.Specifically, electronic device 600 replaces display of app icons612AA-612AK with app icons 612A-612Z, while maintaining display ofwidget 622A, as shown in FIG. 6G.

With reference to FIGS. 6A-6G, electronic device 600 has been in anunlocked state. At FIG. 6G, the user presses the hardware button to lockelectronic device 600. As a result, while concurrently displaying widget622A and app icons 612A-612Z, electronic device 600 detects input 648 athardware button 604. Upon detecting input 648, electronic device 600transitions from an unlocked state to a locked state, as depicted inFIG. 6H.

At FIG. 6H, electronic device 600 is in a locked state, as indicated bylock icon 650. While in a locked state, electronic device 600 displaysuser interface 652 with notifications 654A-654B. The user performs aswipe gesture on user interface 652 to access the widgets. As a result,while displaying user interface 652, electronic device 600 detects swipegesture 656. Upon detecting swipe gesture 656, electronic device 600slides widgets 622A-622E over user interface 652 such that the displayof widgets 622A-622E is overlaid on top of user interface 652, as shownin FIG. 61 . Moreover, electronic device 600 displays search bar 658above widget 622A, where search bar 658 enables a user to search thecontents of electronic device 600 and/or perform a web search. Further,electronic device 600 blurs a portion of the display outside of widgets622A-622E and search bar 658, as indicated by the crosshatching in FIG.61 . It is noted that swipe gesture 656 can cause the above describedresult when electronic device 600 is in an unlocked state as well.

In some embodiments, instead of detecting swipe gesture 656, electronicdevice 600 detects swipe gesture 660 at notification 654B, as shown inFIG. 6H. In some embodiments, upon detecting swipe gesture 660,electronic device does not slide widgets 622A-622E over user interface652, and instead attempts to launch (or display) the application thatcorresponds to notification 654B.

After viewing widgets 622A-622E, the user navigates back to userinterface 652 of FIG. 6H by tapping in a region outside of the widgets.As a result, electronic device returns to displaying user interface 652of FIG. 6H in response to detecting tap gesture 651 in a region outsideof widgets 622A-622E and, optionally, search bar 658.

At FIG. 6H, the user performs a swipe gesture navigate to the homescreen. As a result, while displaying user interface 652, electronicdevice 600 detects swipe gesture 662 starting near the bottom edge ofdisplay 602 with movement in the upward direction. Upon detecting swipegesture 662, electronic device 600 attempts to biometricallyauthenticate the user using biometric sensor 606. Upon successfulauthentication, electronic device 600 replaces display of user interface652 with home screen 608 of FIG. 6J. In particular, electronic device600 concurrently displays widget 622A and app icons 612A-612Z.

At FIG. 6J, the user performs a tap gesture to expand widget 622A andsee additional information from the calendar application. As a result,while concurrently displaying widget 622A and app icons 612A-612Z,electronic device 600 detects tap gesture 664 at expand chevron 666. Insome embodiments, upon detecting tap gesture 664, electronic device 600determines whether expansion criteria is met. In particular, electronicdevice 600 determines whether the widget selected for expansion canexpand downward to a fully expanded size without causing a portion ofthe widget to fail to display. Upon determining that the expansioncriteria is met (e.g., no portion would fail to display due toexpansion), electronic device 600 expands the size of widget 622A toshow more information from the calendar application, as illustrated inFIG. 6K.

At FIG. 6K, electronic device 600 displays widget 622A in an expandedstate. The user performs another tap gesture to collapse widget 622Aback to its original state. As a result, while displaying the expandedversion of widget 622A, electronic device 600 detects tap gesture 668 atcollapse chevron 670. Upon detecting tap gesture 668, electronic device600 collapses the expanded version of widget 622A, as shown in FIG. 6L.

It is noted that electronic device 600 displays a single widget (e.g.,622A) in FIG. 6L. In some embodiments, widget 622A is a “pinned” widget,as discussed above. In some embodiments, a user can scroll the widgetsto see additional widgets that are in the “favorites” category, but notwidgets that are in the “library” category.

At FIG. 6L, the user scrolls the widgets to view additional widgets. Asa result, while concurrently displaying widget 622A and app icons612A-612Z, electronic device 600 detects scroll gesture 672 in widgetregion 628. Upon detecting scroll gesture 672, electronic device 600determines the direction of the movement in scroll gesture 672. Upondetermining that the direction of the movement in scroll gesture 672 isupward, electronic device 600 displays widgets 622B-622C, as shown inFIG. 6M. As depicted in FIG. 6P, widgets 622B-622C are the first twowidgets listed in the “favorites” category. Accordingly, in someembodiments, electronic device 600 selects widgets 622B-622C for displayupon determining that the direction of the movement in scroll gesture672 is upward.

At FIG. 6M, the user performs a tap gesture to expand widget 622C andsee additional information from the news application. As a result, whiledisplaying widget 622C, electronic device 600 detects tap gesture 674 atexpand chevron 676. In some embodiments, upon detecting tap gesture 674,electronic device 600 determines whether expansion criteria is met. Inparticular, electronic device 600 determines whether the widget selectedfor expansion can expand downward to a fully expanded size withoutcausing a portion of the widget to fail to display. Upon determiningthat the expansion criteria is not met (e.g., a portion of the widgetwould fail to display due to expansion), electronic device 600 expandsthe size of widget 622C while also scrolling widgets 622A-622C upward toaccommodate the additional space needed to display widget 622C at itsexpanded size. As a result of scrolling the widgets 622A-622C upward,electronic device 600 ceases to display widget 622A, while timeindicator 624 and date indicator 626 moves from widget region 628 tostatus bar 620, as depicted in FIG. 6N. Notably, time indicator 624 anddate indicator 626 become smaller when moved to the status bar 620.

At FIG. 6N, electronic device 600 displays an expanded version of widget622C, which includes additional information from the news application.The user scrolls the widgets to see additional widgets. As a result,while concurrently displaying widgets 622B-622C and app icons 612A-612Z,electronic device 600 detects scroll gesture 678 in widget region 628.Upon detecting scroll gesture 678 (e.g., an upward swipe gesture),electronic device 600 determines the direction of the movement in scrollgesture 678. Upon determining that the direction of the movement inscroll gesture 678 is upward, electronic device 600 scrolls the widgetssuch that widgets 622B-622C cease to display and widgets 622F-622H aredisplayed, as depicted in FIG. 60 .

At FIG. 6O, the user has reached the end of the scrolled widgets, whereedit button 680 is provided. As depicted in FIG. 6P, widgets 622F-622Hare the last three widgets listed in the “favorites” category.Accordingly, in some embodiments, electronic device 600 selects widgets622F-622H for display upon determining that the direction of themovement in scroll gesture 678 is upward.

Having reached the end of the scrolled widgets, the user performs a tapgesture on edit button 680 to enter an edit mode, as illustrated in FIG.6O. As a result, while concurrently displaying widgets 622F-622H and appicons 612A-612Z, electronic device 600 detects tap gesture 681 at editbutton 680. Upon detecting tap gesture 681, electronic device 600displays edit user interface 682 and causes widgets and app icons toenter an edit mode, as shown in FIG. 6P. In some embodiments, instead ofdetecting tap gesture 681 at edit button 680, electronic device 600detects long press gesture 683 at app icon 612H. In some embodiments,upon detecting long press gesture 683, electronic device 600 displaysedit user interface 682 and causes widgets and app icons to enter anedit mode, as shown in FIG. 6P. Thus, a user can enter the edit mode byeither tapping on edit button 680 or performing a long press on one ofapp icons 612A-612Z.

In the edit mode, the user can perform a variety of functions pertainingto the widgets or app icons. These functions can include reordering thewidgets, moving widgets from one category (e.g., pinned, favorites,library) to another category, removing app icons from the home screen,and reorganizing app icons by changing the placement of app icons on thehome screen. For example, in response to detecting a tap gesture atdelete icon 673, electronic device 600 moves the widget (e.g., 622C)corresponding to delete icon 673 from the “favorites” category to the“library” category. As another example, in response to detecting a tapgesture at add icon 675, electronic device 600 moves the widgetcorresponding to add icon 675 from the “library” category to the“pinned” category or, in some embodiments, the “favorites” category. Asyet another example, in response to detecting a drag gesture at icon677, electronic device 600 moves the widget (e.g., 622B) correspondingto icon 677 to a different location in the list of widgets in accordancewith the movement of the drag gesture. As yet another example, inresponse to detecting a tap gesture at icon 679, electronic device 600initiates a process for deleting the application corresponding to appicon 612, thereby resulting in removal of app icon 612A from home screen608.

At FIG. 6P, the user exits the edit mode by performing a tap gesture ondone button 684. As a result, while displaying edit user interface 682,electronic device 600 detects tap gesture 685 at done button 684. Upondetecting tap gesture 685, electronic device 600 exits the edit mode andreturns to the home screen, as depicted in FIG. 6Q.

At FIG. 6Q, the user performs a tap gesture to navigate to the beginningof the scrolled widgets. As a result, while concurrently displayingwidgets 622F-622H and app icons 612A-612Z, electronic device 600 detectstap gesture 686 at a location above widget region 628 and on status bar620. Upon detecting tap gesture 686, electronic device 600 scrolls tothe beginning of the scrolled widgets, as depicted in FIG. 6R. In someembodiments, instead of detecting tap gesture 686, electronic device 600detects scroll gesture 687 with movement in a downward direction. Insome embodiments, upon detecting scroll gesture 687, electronic device600 scrolls the widgets downward. Thus, the user can navigate to thebeginning of the scrolled widgets using one or more downward scrollgestures or by tapping on status bar 620 above the widgets.

At FIG. 6R, electronic device 600 displays the widgets at the beginningof the scrolled widgets, which includes widgets from the “pinned”category (e.g., 622A) and “favorites” category (e.g., 622B-622C). Theuser performs a scroll gesture to remove “favorites” widgets from beingdisplayed. As a result, while concurrently displaying widgets 622A-622Cand app icons 612A-612Z, electronic device 600 detects scroll gesture688 in widget region 628. Upon detecting scroll gesture 688, electronicdevice 600 determines the direction of the movement in scroll gesture688. Upon determining that the direction of the movement in scrollgesture 688 is downward, electronic device 600 maintains display ofwidget 622A while ceasing the display of widgets 622B-622C, as depictedin FIG. 6S. In some embodiments, while only pinned widget(s) (e.g.,622A) are displayed, electronic device detects a scroll gesture (e.g., adownward swipe gesture) in widget region 628 with movement in thedownward direction. In some embodiments, upon detecting the scrollgesture, electronic device displays a search bar (e.g., 658 in FIG. 61 )in widget region 628, where the search bar enables a user to search thecontents of electronic device 600 and/or perform a web search.

At FIG. 6S, electronic device 600 is operated by the user while thedevice is in a landscape orientation (and thus providing user interfacesfor a landscape view). The user then rotates electronic device 600clockwise (with respect to the user) so the user can use the device in aportrait orientation. As a result, while concurrently displaying widget622A and app icons 612A-612Z, electronic device 600 detects a change inorientation of the device to a portrait orientation (and thus providesuser interfaces for a portrait view). Upon detecting the change inorientation, electronic device 600 removes widgets from home screen 608and reverts to displaying the first page of app icons. As a result,electronic device 600 ceases to display widget 622A but continues todisplay app icons 612A-612Z, as shown in FIG. 6T. Due to the change inorientation of the device, app icons 612A-612Z are displayed in newlocations on display 602 and in new orientations relative to the device.

At FIG. 6T, electronic device 600 displays app icons 612A-612Z while thedevice is in a portrait orientation. While displaying app icons612A-612Z without widget(s), electronic device 600 detects swipe gesture689 in a region corresponding to (e.g., occupied by) app icons612A-612Z. Upon detecting swipe gesture 689, electronic device 600determines the direction of the movement in swipe gesture 689. Upondetermining that the direction of the movement in swipe gesture 689 isleft-to-right, electronic device 600 replaces display of the first pageof app icons with display of the page of widget(s). As a result,electronic device 600 replaces display of app icons 612A-612Z withdisplay of widgets 622A-622G, as depicted in FIG. 6U.

FIG. 6V depicts an alternative embodiment for displaying widgets whilethe device is in a portrait orientation. Referring back to FIG. 6T,electronic device 600 detects swipe gesture 689 in a regioncorresponding to app icons 612A-612Z while the device is in a portraitorientation. Upon determining that the direction of the movement inswipe gesture 689 is left-to-right, electronic device 600 replacesdisplay of the first page of app icons with display of the page ofwidget(s), as depicted in FIG. 6U. In some embodiments, instead ofreplacing display of the first page of app icons, electronic device 600overlays the display of the widget(s) on top of the first page of appicons, as depicted in FIG. 6V. As a result, electronic device 600displays widgets 622A-622F overlaid on top of app icons 612A-612Z. Insome embodiments, displaying the widgets on top of the app iconsincludes reducing the displayed size of app icons 612A-612Z.

At FIG. 6U, the user navigates back to the first page of app icons via aright-to-left swipe gesture. As a result, electronic device 600 detectsswipe gesture 696 and, in response, replaces display of the page ofwidget(s) with the first page of app icons, as depicted in FIG. 6W.

At FIG. 6W, the user performs a swipe gesture to navigate to the secondpage of app icons. As a result, while displaying app icons 612A-612Zwithout widget(s), electronic device 600 detects swipe gesture 690 in aregion corresponding to (e.g., occupied by) app icons 612A-612Z. Upondetecting swipe gesture 690, electronic device 600 determines thedirection of the movement in swipe gesture 690. Upon determining thatthe direction of the movement in swipe gesture 690 is right-to-left,electronic device 600 replaces display of the first page of app iconswith the second page of app icons. As a result, the display of app icons612A-612Z is replaced with the display of app icons 612AA-612AK, asshown in FIG. 6X. At FIG. 6X, the user then navigates back to the firstpage of app icons by performing a left-to-right swipe gesture. As aresult, electronic device 600 detects swipe gesture 695, and inresponse, replaces display of the second page of app icons with thefirst page of app icons, as shown in FIG. 6W.

At FIG. 6W, electronic device 600 is operated by the user while thedevice is in a portrait orientation. The user rotates the devicecounterclockwise to return the device back to a landscape orientation.As a result, while displaying app icons 612A-612Z without widget(s),electronic device 600 detects a change in orientation of the device fromportrait orientation to landscape orientation. Upon detecting the changein orientation, electronic device 600 again merges the page of widget(s)onto home screen 608, as discussed above with respect to FIG. 6B-6C. Asa result, electronic device 600 concurrently displays widget 622A andapp icons 612A-612Z, as depicted in FIG. 6Y. Thus, the previous state ofthe home screen in the landscape orientation persists despite theintervening display of the home screen in a portrait orientation. Insome embodiments, instead of concurrently displaying widget 622A and appicons 612A-612Z upon detecting the change in orientation, electronicdevice 600 returns to the home screen depicted in FIG. 6A. Specifically,electronic device 600 displays app icons 612A-612Z without widget 622A.

At FIG. 6Y, the user performs a swipe gesture to remove the widgets fromthe home screen. As a result, while concurrently displaying widget 622Aand app icons 612A-612Z on home screen 608, electronic device 600detects swipe gesture 691 with movement in the right-to-left direction.In some embodiments, upon detecting swipe gesture 691, electronic device600 determines the region in which swipe gesture 691 was detected. Upondetermining that swipe gesture 691 was detected in widget region 628,electronic device 600 collapses widget region 628 and removes widgetsfrom home screen 608. As a result, electronic device 600 ceases displayof widget 622A, and expands the region that app icons 612A-612Z occupy,as depicted in FIG. 6Z. As a result, the spacing between the app iconsin app icons 612A-612Z increases.

It is noted that the above described result in FIGS. 6Z occurs as aresult of detecting a right-to-left swipe gesture in widget region 628.For the result that occurs due to detecting a right-to-left swipegesture in app region 630, refer to the description above with respectto FIGS. 6E-6F. For the result that occurs due to detecting aleft-to-right swipe gesture in widget region 628, refer to thedescription below with respect to FIG. 6AC.

At FIG. 6Z, electronic device 600 displays the first page of app iconswithout widget(s). The user performs a swipe gesture to navigate to thesecond page of app icons. As a result, while displaying app icons612A-612Z without widget(s), electronic device 600 detects swipe gesture692 in a region corresponding to (e.g., occupied by) app icons612A-612Z. Upon detecting swipe gesture 692, electronic device 600determines the direction of the movement in swipe gesture 692. Upondetermining that the direction of the movement in swipe gesture 692 isright-to-left, electronic device 600 replaces display of the first pageof app icons with the second page of app icons. As a result, display ofapp icons 612A-612Z is replaced with display of app icons 612AA-612AK,as shown in FIG. 6AA.

FIG. 6AB depicts an alternative embodiment for displaying a widget at anexpanded size. With reference to FIG. 6O, electronic device 600 detectslong press gesture 693 at widget 622G. Upon detecting long press gesture693, electronic device 600 displays an expanded version of widget 622G,as illustrated in FIG. 6AB. In particular, electronic device 600 expandsthe size of widget 622G and displays additional information from thestock application. Further, upon detecting long press gesture 693,electronic device 600 blurs a portion of display 602 outside of theexpanded version of widget 622G, as indicated by the crosshatching inFIG. 6AB, and generates a tactile output (e.g., haptic feedback). Insome embodiments, the app icons also shrink in size upon detecting longpress gesture 693. In some embodiments, a hard press gesture (e.g., apress that exceeds a threshold amount of contact intensity) triggers thesame result as described above with respect to long press gesture 693.

FIG. 6AC illustrates the displayed result of detecting a swipe gesturewith movement in the left-to-right direction while concurrentlydisplaying widget(s) and the first page of app icons. With reference toFIG. 6C, electronic device 600 concurrently displays widget 622A and thefirst page of app icons. In some embodiments, electronic device 600detects a swipe gesture in widget region 628 or app region 630 withmovement in the left-to-right direction. Upon detecting the swipegesture with movement in the left-to-right direction, electronic device600 provides an indication that no content is available to the left ofthe currently displayed content. In particular, electronic device 600shifts the display of widget 622A and app icons 612A-612Z to the rightas shown in FIG. 6AC, followed by immediately shifting the display ofwidget 622A and app icons 612A-612Z back to the left to return widget622A and app icons 612A-612Z back to their respective locations in FIG.6C. Moreover, upon detecting the swipe gesture with movement in theleft-to-right direction, electronic device 600 displays grabberindicator 694, which provides an indication to the user that widgetregion 628 can be interacted with via user gestures. For example, asillustrated in FIGS. 6X-6Y, the user can collapse widget region 628,thereby causing the widget(s) to cease to display.

FIGS. 7A-7B are a flow diagram illustrating a method for displayingwidgets using an electronic device in accordance with some embodiments.Method 700 is performed at an electronic device (e.g., 100, 300, 500,600) with a display device (e.g., 602). Some operations in method 700are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for displayingwidgets. The method reduces the cognitive burden on a user fordisplaying widgets, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user todisplay widgets faster and more efficiently conserves power andincreases the time between battery charges.

An electronic device (e.g., 100, 300, 500, 700) displays (702), via thedisplay device (e.g., 602), a first plurality of application icons(e.g., 612A-612Z) (e.g., a plurality of icons on a first page) withoutdisplaying a first set of one or more user interface elements (e.g.,622A) (e.g., without displaying widgets), wherein the application iconsare selectable to display application user interfaces (e.g., 636) forcorresponding applications (e.g., by the device detecting, on atouch-sensitive surface (e.g., of display 602), a tap gesture (e.g.,634) at a location (on the touch-sensitive surface) corresponding to adisplayed location of the respective application icon (e.g., 612I)). Insome embodiments, the first plurality of application icons (e.g.,612A-612Z) are displayed on a home screen (e.g., 608). In someembodiments, the first plurality of application icons are displayedwithout displaying a second plurality of application icons (e.g.,612AA-612AK) that are different from the first plurality of applicationicons.

While displaying, via the display device (e.g., 602), the firstplurality of application icons (e.g., 612A-612Z), the electronic devicedetects (704) a first user input (e.g., 618, 692) (e.g., a user gesture,swipe, drag). In some embodiments, the first user input is detected in aregion occupied by the first plurality of application icons.

In response (706) to detecting the first user input (e.g., 618, 692): inaccordance (708) with a determination that the first user input includesmovement in a first direction (e.g., left, right, up, down) (e.g., thedirection is relative to the displayed user interface (e.g., 608))(e.g., a determination that a first set of criteria is met, including arequirement that the first user input includes movement in a firstdirection and, optionally, that the orientation of the electronic deviceis in a first orientation): the electronic device ceases (710) displayof the first plurality of application icons (e.g., 612A-612Z) (e.g., bysliding the first plurality of application icons off the display device(e.g., 602) in the first direction), and displays (712) (e.g., initiallydisplays), via the display device, a second plurality of applicationicons (e.g., 612AA-612AK) that are different from the first plurality ofapplication icons (e.g., without displaying widget(s) (e.g., 622A-622H)(e.g., user interface elements)), wherein the application icons areselectable to display application user interfaces for correspondingapplications. Thus, the technique replaces display of the firstplurality of application icons (e.g., 612A-612Z) with display of thesecond plurality of application icons (e.g., 612AA-612AK). In someembodiments, the determination is made by the electronic device. In someembodiments, the determination is made by a device external to theelectronic device.

In response (706) to detecting the first user input (e.g., 618, 692): inaccordance (714) with a determination that the first user input includesmovement in a second direction (e.g., left, right, up, down) (e.g., thedirection is relative to the displayed user interface (e.g., 608)) thatis different from (e.g., substantially opposite to) the first direction(e.g., a determination that a second set of criteria is met, including arequirement that the first user input includes movement in a seconddirection and, optionally, that the orientation of the electronic deviceis in the first orientation): the electronic device modifies (716)(e.g., resizes) display of the first plurality of application icons(e.g., 612A-612Z) to change (e.g., to reduce) a distance between (e.g.,the centers of, the edges of) a first application icon (e.g., 612A) ofthe first plurality of application icons and a second application icon(e.g., 612B) of the first plurality of application icons, andconcurrently displays (718), via the display device, the modified firstplurality of application icons (e.g., 612A-612Z) and the first set ofone or more user interface elements (e.g., 622A) (e.g., withoutconcurrently displaying the second plurality of application icons (e.g.,612AA-612AK)). Modifying display of the first plurality of applicationicons to change a distance between the first application icon and thesecond application icon enables concurrent display of the firstplurality of application icons and the first set of one or more userinterface elements. This is in contrast to ceasing display of the firstplurality of application icons, which would necessitate additional userinputs to access the first plurality of application icons. Accordingly,modifying display of the first plurality of application icons to allowfor concurrent display reduces the number of inputs needed forperforming operations pertaining to the application icons and the userinterface elements. Reducing the number of inputs needed to perform anoperation enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the distance that changes between the applicationicons (e.g., 612A-612Z) is a horizontal distance. In some embodiments,the vertical distance between the first application icon and the secondapplication icon does not change. In some embodiments, horizontal andvertical is relative to the displayed user interface (e.g., 608) or thedevice itself. In some embodiments, a user interface element (e.g.,622A-622H) (e.g., of the one or more user interface elements includesdisplayed content related to or corresponding to an application. In someembodiments, the modified first plurality of application icons (e.g.,612A-612Z) are displayed adjacent to the first set of one or more userinterface elements (e.g., 622A). In some embodiments, the modified firstplurality of application icons and the first set of one or more userinterface elements are displayed on the home screen (e.g., 608). In someembodiments, the first set of one or more user interface elementsincludes only the pinned user interface elements (e.g., 622A) (e.g.,user interface elements that are designated as a special category)regardless of the last state at which the user interface elements weredisplayed. In some embodiments, the first set of one or more userinterface elements are selected for display based on the last state.That is, the device displays one or more of (e.g., all of) the userinterface elements (e.g., 622A-622H) that were displayed during the laststate. In some embodiments, the determination is made by the electronicdevice. In some embodiments, the determination is made by a deviceexternal to the electronic device.

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the modified first plurality of application icons(e.g., 612A-612Z) and the first set of one or more user interfaceelements (e.g., 622A), the electronic device detects a second user input(e.g., 634, 638) (e.g., a user gesture, tap). In some embodiments, inresponse to detecting the second user input: in accordance with adetermination that the second user input corresponds to selection of anapplication icon (e.g., 612I) of the modified first plurality ofapplication icons, the electronic device displays (e.g., initiallydisplays), via the display device, a user interface (e.g., 636) of anapplication corresponding to the selected application icon.

In some embodiments, displaying the user interface (e.g., 636) of anapplication corresponding to the selected application icon (e.g., 612I)includes replacing concurrent display of the modified first plurality ofapplication icons (e.g., 612A-612Z) and the first set of one or moreuser interface elements (e.g., 622A) with display of the user interfaceof the application corresponding to the selected application icon. Insome embodiments, displaying the user interface of the applicationoccurs as a result of launching the application corresponding to theselected application icon.

In some embodiments, the selected application icon (e.g., 612I) and auser interface element (e.g., 622A) of the first set of one or more userinterface elements correspond to the same application. In someembodiments, in response to detecting the second user input (e.g., 634,638): in accordance with a determination that the second user inputcorresponds to selection of the user interface element of the first setof one or more user interface elements (e.g., an app icon (e.g., 640)corresponding to the user interface element), the electronic devicedisplays (e.g., initially displays), via the display device (e.g., 602),a user interface (e.g., 636) of an application corresponding to theselected user interface element, wherein the application correspondingto the selected user interface element is the same as the applicationcorresponding to the selected application icon.

In some embodiments, the user interface (e.g., 636) of the applicationcorresponding to the selected user interface element (e.g., 622A) is thesame user interface as the user interface of the applicationcorresponding to the selected application icon (e.g., 612I). In someembodiments, displaying the user interface (e.g., 636) of theapplication corresponding to the selected user interface element (e.g.,622A) includes replacing concurrent display of the modified firstplurality of application icons (e.g., 612A-612Z) and the first set ofone or more user interface elements (e.g., 622A) with display of theuser interface of the application corresponding to the selected userinterface element. In some embodiments, displaying the user interface(e.g., 636) of the application occurs as a result of launching theapplication corresponding to the selected user interface element (e.g.,622A). In some embodiments, the user interface element (e.g., 622A)includes displayed information received from an applicationcorresponding to the user interface element.

In some embodiments, while displaying, via the display device (e.g.,602), the user interface (e.g., 636) of the application corresponding tothe selected application icon, the electronic device detects a userrequest (e.g., 642) to navigate to a home screen (e.g., 608) (e.g., auser input (e.g., swipe in the up direction) starting at a locationproximate to the bottom edge of the device or activation of a physicalor virtual home button). In some embodiments, the home screen (e.g.,6-608) includes the first plurality of application icons (e.g.,612A-612Z). In some embodiments, the user interface (e.g., 636) of theapplication corresponding to the selected application is displayedwithout displaying the modified first plurality of application icons(e.g., 612A-612Z) and/or the first set of one or more user interfaceelements (e.g., 622A).

In some embodiments, in response to detecting the user request (e.g.,642) to navigate to the home screen, the electronic device replacesdisplay of the user interface (e.g., 636) of the applicationcorresponding to the selected application with display of the homescreen (e.g., 608), wherein displaying the home screen includesconcurrently displaying, via the display device, the modified firstplurality of application icons (e.g., 612A-612Z) and the first set ofone or more user interface elements (e.g., 622A). Concurrentlydisplaying the first plurality of application icons and the first set ofone or more user interface elements after having displayed a userinterface of an application enables a user to quickly regain access tothe user interface elements. This is in contrast to ceasing display ofthe first set of one or more user interface elements after havingdisplayed the user interface of the application, which would necessitateadditional user inputs to access the user interface elements.Accordingly, concurrent display of the first plurality of applicationicons and the first set of one or more user interface elements inresponse to detecting the user request reduces the number of inputsneeded for performing operations pertaining to the user interfaceelements. Reducing the number of inputs needed to perform an operationenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the modified first plurality of application icons(e.g., 612A-612Z) and the first set of one or more user interfaceelements (e.g., 622A), the electronic device detects a first paginginput (e.g., 644) (e.g., that includes movement in the first directionsuch as a swipe gesture in the first direction). In some embodiments,the first paging input (e.g., 644) is detected in a region (e.g., 630)occupied by the modified first plurality of application icons (e.g.,612A-612Z). In some embodiments, the first paging input (e.g., 644) isdetected in a region (e.g., 630) that does not correspond to (e.g., isnot occupied by) the first set of one or more user interface elements(e.g., 622A), the status bar (e.g., 620), and the dock region (e.g.,610).

In some embodiments, in response to detecting the paging input (e.g.,644), the electronic device displays, via the display device (e.g.,602), the second plurality of application icons (e.g., 612AA-612AK) thatare different from the first plurality of application icons (and,optionally ceases to display the modified first plurality of applicationicons (e.g., 612A-612Z) and the first set of one or more user interfaceelements (e.g., 622A)).

In some embodiments, while displaying, via the display device (e.g.,602), the second plurality of application icons (e.g., 612AA-612AK), theelectronic device detects a second paging input (e.g., 646) (e.g., thatincludes movement in the second direction such as a swipe gesture in thesecond direction). In some embodiments, the second plurality ofapplication icons are displayed without displaying the modified firstplurality of application icons (e.g., 612A-612Z) and/or the first set ofone or more user interface elements (e.g., 622A). In some embodiments,the second paging input (e.g., 646) is detected in a region (e.g., 630)occupied by the second plurality of application icons (e.g.,612AA-612AK). In some embodiments, the second paging input is detectedin a region (e.g., 630) that does not correspond to (e.g., is notoccupied by) the first set of one or more user interface elements (e.g.,622A), the status bar (e.g., 620), and the dock region (e.g., 610).

In some embodiments, in response to detecting the second paging input(e.g., 646), the electronic device replaces display of the secondplurality of application icons (e.g., 612AA-612AK) with display of themodified first plurality of application icons (e.g., 612A-612Z) and thefirst set of one or more user interface elements (e.g., 622A).Concurrently displaying the first plurality of application icons and thefirst set of one or more user interface elements after having displayedthe second plurality of application icons enables a user to quicklyregain access to the user interface elements. This is in contrast toceasing display of the first set of one or more user interface elementsafter having displayed the second page of application icons, which wouldnecessitate additional user inputs to access the user interfaceelements. Accordingly, concurrent display of the first plurality ofapplication icons and the first set of one or more user interfaceelements in response to detecting the second paging input reduces thenumber of inputs needed for performing operations pertaining to the userinterface elements. Reducing the number of inputs needed to perform anoperation enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the modified first plurality of application icons(e.g., 612A-612Z) and the first set of one or more user interfaceelements (e.g., 622A), the electronic device detects a user request(e.g., input 648 at hardware button 604) (while in an unlocked state) totransition the electronic device to a locked state. In some embodiments,in response to detecting the user request to transition the electronicdevice to the locked state: the electronic device transitions theelectronic device from an unlocked state to the locked state, and ceasesdisplay of the modified first plurality of application icons (e.g.,612A-612Z) and the first set of one or more user interface elements(e.g., 622A) (e.g., including transitioning the display device to aninactive state (e.g., off, a state in which nothing is displayed) ordisplaying a wake screen user interface (e.g., 652)).

In some embodiments, while the electronic device is in the locked state,the electronic device detects one or more inputs (e.g., 662, biometricinput) to transition the electronic device to an unlocked state andnavigate to the home screen (e.g., 608) (e.g., detecting change inorientation of device, detecting user input (e.g., 662) at displaydevice (e.g., 602) (e.g., tap gesture, swipe gesture starting near anedge of the display device, information corresponding to a biometricfeature (e.g., fingerprint, face))). In some embodiments, in response todetecting the one or more inputs: the electronic device transitions theelectronic device from the locked state to the unlocked state, andconcurrently displays, via the display device (e.g., 602), the modifiedfirst plurality of application icons (e.g., 612A-612Z) and the first setof one or more user interface elements (e.g., 622A). In someembodiments, the electronic device maintains the state of what isdisplayed prior to locking of the device. Concurrently displaying thefirst plurality of application icons and the first set of one or moreuser interface elements after being in a locked state enables a user toquickly regain access to the user interface elements. This is incontrast to ceasing display of the first set of one or more userinterface elements after being in a locked state, which wouldnecessitate additional user inputs to access the user interfaceelements. Accordingly, concurrent display of the first plurality ofapplication icons and the first set of one or more user interfaceelements in response to the one or more inputs reduces the number ofinputs needed for performing operations pertaining to the user interfaceelements. Reducing the number of inputs needed to perform an operationenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the first user input (e.g., 618, 692) is detectedwhile the electronic device (e.g., a displayed user interface (e.g.,608)) is in a first orientation (e.g., portrait orientation, landscapeorientation). In some embodiments, ceasing display of the firstplurality of application icons (e.g., 612A-612Z), displaying the secondplurality of application icons (e.g., 612AA-612AK), modifying display ofthe first plurality of application icons, and/or concurrently displayingthe modified first plurality of application icons and the first set ofone or more user interface elements (e.g., 622A) occur while theelectronic device is in the first orientation.

In some embodiments, while displaying, via the display device (e.g.,602), the first plurality of application icons (e.g., 612A-612Z), theelectronic device detects a third user input (e.g., 689, 690) (e.g., auser gesture, swipe, drag) that is different from the first user input,wherein the third user input is detected while the electronic device(e.g., a displayed user interface) is in a second orientation (e.g.,portrait orientation, landscape orientation) that is different from thefirst orientation.

In some embodiments, in response to detecting the third user input(e.g., 689, 690): in accordance with a determination that the detectedthird user input includes movement in a third direction (e.g., left,right, up, down) (e.g., the direction is relative to the displayed userinterface (e.g., 608)) (e.g., a determination that a third set ofcriteria is met, including a requirement that the third user inputincludes movement in a third direction and, optionally, that theorientation of the electronic device is in the second orientation): theelectronic device ceases display of the first plurality of applicationicons (e.g., 612A-612Z) (e.g., by sliding the first plurality ofapplication icons off the display device (e.g., 602) in the thirddirection), and displays (e.g., initially displays), via the displaydevice (e.g., 602), the second plurality of application icons (e.g.,612AA-612AK) that are different from the first plurality of applicationicons (e.g., without displaying widgets (e.g., 622A-622H)), wherein theapplication icons are selectable to display application user interfacesfor corresponding applications. Thus, the technique replaces display ofthe first plurality of application icons (e.g., 612A-612Z) with displayof the second plurality of application icons (e.g., 612AA-612AK). Insome embodiments, the first direction and the third direction are in thesame direction relative to the displayed user interface (e.g., 608).

In some embodiments, in response to detecting the third user input(e.g., 689, 690): in accordance with a determination that the detectedthird user input includes movement in a fourth direction (e.g., left,right, up, down) (e.g., the direction is relative to the displayed userinterface (e.g., 608)) that is different from (e.g., substantiallyopposite to) the third direction (e.g., a determination that a fourthset of criteria is met, including a requirement that the third userinput includes movement in a fourth direction and, optionally, that theorientation of the electronic device is in the second orientation): theelectronic device ceases display of the first plurality of applicationicons (e.g., 612A-612Z) (e.g., by sliding the first plurality ofapplication icons off the display device (e.g., 602) in the thirddirection), and displays (e.g., initially displays), via the displaydevice (e.g., 602), the first set of one or more user interface elements(e.g., 622A) (e.g., without concurrently displaying the second pluralityof application icons (e.g., 612AA-612AK) (or any application icons inthe second plurality of application icons)). Thus, the techniquereplaces display of the first plurality of application icons (e.g.,612A-612Z) with display of the first set of one or more user interfaceelements (e.g., 622A). In some embodiments, the second direction and thefourth direction are in the same direction relative to the displayeduser interface (e.g., 608).

In some embodiments, while displaying, via the display device (e.g.,602), the first plurality of application icons (e.g., 612A-612Z), theelectronic device detects a third user input (e.g., 689, 690) (e.g., auser gesture, swipe, drag) that is different from the first user input,wherein the third user input is detected while the electronic device(e.g., a displayed user interface) is in a second orientation (e.g.,portrait orientation, landscape orientation) that is different from thefirst orientation. In some embodiments, the third input is detectedwhile the electronic device is in the first orientation. Thus, the userinterface elements slide over the application icons regardless of theorientation of the electronic device.

In some embodiments, in response to detecting the third user input(e.g., 689, 690), the electronic device displays (e.g., initiallydisplays), via the display device (e.g., 602), the first set of one ormore user interface elements (e.g., 622A), wherein the first set of oneor more user interface elements are overlaid on top of a portion of thefirst plurality of application icons (e.g., 612A-612Z). In someembodiments, displaying, via the display device (e.g., 602), the firstset of one or more user interface elements (e.g., 622A) includes slidingthe first set of one or more user interface elements onto the displaydevice from an edge of the display device. In some embodiments, the edgeof the display device (e.g., 602) is proximate to the location at whichthe third user input was detected. In some embodiments, maintainingdisplay of the first plurality of application icons (e.g., 612A-612Z)includes reducing the size of the first plurality of application iconsand/or blurring the first plurality of application icons.

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the modified first plurality of application icons(e.g., 612A-612Z) and the first set of one or more user interfaceelements (e.g., 622A), the electronic device detects a user request(e.g., swipe, drag in the up/down direction) to vertically scroll thefirst set of one or more user interface elements. In some embodiments,the user request is a user request to scroll the user interface elements(e.g., 622A-622H). In some embodiments, the user request includes agesture (e.g., swipe, drag) starting in a region (e.g., 628)corresponding to the user interface elements (e.g., 622A-622H) (e.g., aregion that does not overlap with a region (e.g., 630) corresponding tothe application icons (e.g., 612A-612AK)).

In some embodiments, in response to detecting the user request tovertically scroll the first set of one or more user interface elements(e.g., 622A), the electronic device vertically scrolls the first set ofone or more user interface elements, wherein a portion of the first setof one or more user interface elements ceases to be displayed, and aportion of a second set of one or more user interface elements isdisplayed (e.g., 622B-622H) (e.g., initially displayed). In someembodiments, the first set of one or more user interface elements (e.g.,622A) ceases to display at the same time as when the portion of thesecond set of one or more user interface elements is displayed.

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the modified first plurality of application icons(e.g., 612A-612Z) and the first set of one or more user interfaceelements (e.g., 622A), the electronic device detects (720) a fourth userinput (e.g., 672) (e.g., user gesture, swipe, drag) in a predefinedregion (e.g., 628) corresponding to the first set of one or more userinterface elements (e.g., the predefined region is occupied by the firstset of one or more user interface elements, the predefined region is notoccupied by the first plurality of application icons (e.g., 612A-612Z)),wherein the first set of one or more user interface elements includes asingle user interface element (e.g., 622A) (e.g., displayed at aparticular location on the display device (e.g., 602)).

In some embodiments, in response (722) to detecting the fourth userinput (e.g., 672): in accordance (724) with a determination that thefourth user input includes movement in a fifth direction (e.g., up,down, left, right): the electronic device maintains (726) display of thesingle user interface element (e.g., 622A), and displays (728) (e.g.,initially displays), via the display device (e.g., 602), a second set ofone or more user interface elements (e.g., 622B-622C), wherein thesingle user interface element and the second set of one or more userinterface elements are concurrently displayed. In some embodiments, thesingle user interface element (e.g., 622A) remains at the particularlocation on the display device (e.g., 602). In some embodiments, thesecond set of one or more user interface elements (e.g., 622B-622C) isdisplayed proximate to (e.g., below) the first set of one or more userinterface elements (e.g., 622A). In some embodiments, in accordance witha determination that the fourth user input includes movement in a sixthdirection that is different (e.g., substantially opposite to) from thefifth direction, the electronic device ceases display of the single userinterface element (e.g., 622A) and displays a search bar (e.g., 658).

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the single user interface element (e.g., 622A) andthe second set of one or more user interface elements (e.g., 622B-622C),the electronic device detects a fifth user input (e.g., 688) (e.g., usergesture, swipe, drag (in an up/down direction)). In some embodiments, inresponse to detecting the fifth user input (e.g., 688): the electronicdevice ceases display of the second set of one or more user interfaceelements (e.g., 622B-622C), and maintains display of the single userinterface element (e.g., 622A). In some embodiments, the fifth userinput is detected in the predefined region (e.g., 628). In someembodiments, the single user interface element remains at the particularlocation on the display device (e.g., 602).

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the modified first plurality of application icons(e.g., 612A-612Z) and a third set of one or more user interface elements(e.g., 622F-622H), the electronic device detects a user request (e.g.,681, 683) to enter an edit mode (e.g., corresponding to 682) at alocation corresponding to an application icon (e.g., 612H) of themodified first plurality of application icons (e.g., 612A-612Z) (e.g.,long press on an application icon). In some embodiments, the userrequest is detected in the app region (e.g., 630). In some embodiments,the third set is the same as the first set of one or more user interfaceelements (e.g., 622A). In some embodiments, the edit mode enablesediting (e.g., moving, reordering, reorganizing) of the applicationicons (e.g., 612A-612AK) and user interface elements (e.g., 622A-622H).For example, the user interface elements can have hierarchicalcategories (e.g., pinned, favorites, library). In some embodiments, theedit mode enables reorganizing of the user interface elements into thedifferent hierarchical categories. In some embodiments, entering theedit mode includes displaying delete affordances (e.g., 673, 679) forapplication icons and user interface elements. In some embodiments,entering the edit mode includes enabling reorganizing (e.g., movementfrom an original location to a new location) of application icons anduser interface elements via (e.g., in response to) gestures (e.g., drag,tap). In some embodiments, the user request to enter the edit mode isdetected while concurrently displaying the modified first plurality ofapplication icons (e.g., 612A-612Z) and the first set of one or moreuser interface elements (e.g., 622A).

In some embodiments, in response to detecting the user request (e.g.,681, 683) to enter the edit mode, the electronic device causes one ormore user interface elements (e.g., 622A-622H) (e.g., first set, secondset, third set, or a combination thereof) and application icons (e.g.,612A-612AK) to enter an edit mode. In some embodiments, detecting theuser request at a location corresponding to a user interface element(e.g., long press on the user interface element) also causes the userinterface elements and application icons to enter an edit mode.

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the modified first plurality of application icons(e.g., 612A-612Z) and a third set of one or more user interface elements(e.g., 622F-622H), the electronic device detects a user request (e.g.,681, 683) to enter an edit mode at a location corresponding to an editaffordance (e.g., 680) that is displayed proximate to the third set ofuser interface elements (e.g., tap gesture). In some embodiments, theuser request is detected in the widget region (e.g., 628). In responseto detecting the user request to enter the edit mode, the electronicdevice causes one or more user interface elements (e.g., 622A-622H)(e.g., first set, second set, third set, or a combination thereof) andapplication icons (e.g., 612A-612AK) to enter an edit mode.

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the modified first plurality of application icons(e.g., 612A-612Z) and the first set of one or more user interfaceelements (e.g., 622A), the electronic device detects (730) a change inorientation of the electronic device from a first orientation (e.g.,landscape orientation, portrait orientation) to a second orientation(e.g., portrait orientation, landscape orientation) that is differentfrom the first orientation. In some embodiments, in response (732) todetecting the change in orientation of the electronic device from thefirst orientation to the second orientation, the electronic devicedisplays (734) the first plurality of application icons (e.g.,612A-612Z) without displaying the first set of one or more userinterface elements (e.g., 622A). In some embodiments, in response todetecting the change in orientation of the electronic device from thefirst orientation to the second orientation, changing (e.g., increasing)the distance between a first application icon (e.g., 612A) and a secondapplication icon (e.g., 612B) of the first plurality of applicationicons (e.g., 612A-612Z). Automatically ceasing to display the first setof one or more user interface elements in response to detecting a changein orientation allows the device to maintain display of the firstplurality of application icons in the new orientation. Performing anoperation when a set of conditions has been met without requiringfurther user input enhances the operability of the device (e.g.,maintains accessibility of the first plurality of application icons) andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while displaying the first plurality of applicationicons (e.g., 612A-612Z) without displaying the first set of one or moreuser interface elements (e.g., 622A), the electronic device detects achange in orientation of the electronic device from the secondorientation to the first orientation. In some embodiments, in responseto detecting the change in orientation of the electronic device from thesecond orientation to the first orientation, the electronic deviceconcurrently displays, via the display device (e.g., 602), the modifiedfirst plurality of application icons (e.g., 612A-612Z) and the first setof one or more user interface elements (e.g., 622A). Concurrentlydisplaying the first plurality of application icons and the first set ofone or more user interface elements after reverting back to the device'sprevious orientation enables a user to quickly regain access to the userinterface elements. This is in contrast to ceasing display of the firstset of one or more user interface elements after a change in theorientation of the device, which would necessitate additional userinputs to access the user interface elements. Accordingly, concurrentdisplay of the first plurality of application icons and the first set ofone or more user interface elements in response to the change inorientation reduces the number of inputs needed for performingoperations pertaining to the user interface elements. Reducing thenumber of inputs needed to perform an operation enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, a user interface element (e.g., 622A) of the firstset of user interface elements includes a first set of information froman application corresponding to the user interface element. In someembodiments, while concurrently displaying, via the display device(e.g., 602), the modified first plurality of application icons (e.g.,612A-612Z) and the first set of one or more user interface elements(e.g., 622A), the electronic device detects a user request (e.g., 666,674) to expand the user interface element, wherein a portion (e.g., topportion, bottom portion) of the user interface element is displayed at afirst location on the display device (e.g., 602). In some embodiments,in response to detecting the user request (e.g., 666, 674) to expand theuser interface element: in accordance with a determination thatexpansion criteria is met (e.g., expansion criteria includes arequirement that the displayed user interface element (e.g., 622A) doesnot get cropped due to expansion of the user interface element (e.g., noportion of the displayed user interface element ceases to display as aresult of expanding the user interface element)): the electronic deviceexpands the size of the user interface element (e.g., 622A) whilemaintaining the portion of the user interface element (e.g., 622A) atthe first location on the display device (e.g., 602), and displays(e.g., initially displays), via the display device (e.g., 602), a secondset of information from the application corresponding to the userinterface element, wherein the second set of information is differentfrom the first set of information. In some embodiments, the second setof information is concurrently displayed with the first set ofinformation.

In some embodiments, further in response to detecting the user request(e.g., 666, 674) to expand the user interface element (e.g., 622C): inaccordance with a determination that expansion criteria is not met: theelectronic device expands the size of the user interface element,scrolls the user interface element, wherein scrolling the user interfaceelement (e.g., 622C) causes the portion of the user interface element tobe displayed at a second location on the display device (e.g., 602) thatis different from the first location, and displays (e.g., initiallydisplays), via the display device (e.g., 602), the second set ofinformation from the application corresponding to the user interfaceelement, wherein the second set of information is different from thefirst set of information. In some embodiments, the second set ofinformation is concurrently displayed with the first set of information.Automatically scrolling the user interface element based on adetermination that expansion criteria is not met allows the user to viewthe full contents of the user interface element. Otherwise, additionalinputs would be required to further scroll the user interface element.Performing an operation when a set of conditions has been met withoutrequiring further user input enhances the operability of the device(e.g., maintains accessibility of the first plurality of applicationicons) and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while concurrently displaying, via the displaydevice (e.g., 602), the modified first plurality of application icons(e.g., 612A-612Z) and the first set of one or more user interfaceelements (e.g., 622A), the electronic device detects a sixth user input(e.g., 644, 691) (e.g., user gesture, swipe, drag) with movement in aseventh direction (e.g., left, right, up, down). In some embodiments, inresponse to detecting the sixth user input (e.g., 644, 691): inaccordance with a determination that the sixth user input (e.g., thestart of the user input, the end of the user input) with movement in theseventh direction is detected in a predefined region (e.g., 628)corresponding to the first set of one or more user interface elements(e.g., 622A) (e.g., the predefined region is occupied by the first setof one or more user interface elements, the predefined region is notoccupied by the first plurality of application icons (e.g., 612A-612Z)):the electronic device displays, via the display device (e.g., 602), thefirst plurality of application icons (e.g., 612A-612Z), and ceasesdisplay of the first set of one or more user interface elements (e.g.,622A). In some embodiments, the distance between the first applicationicon and the second application icon of the first plurality ofapplication icons is increased in response to detecting the sixth userinput.

In some embodiments, in response to detecting the sixth user input(e.g., 644, 691): in accordance with a determination that the sixth userinput (e.g., the start of the user input, the end of the user input)with movement in the seventh direction is detected in a predefinedregion (e.g., 630) corresponding to the modified first plurality ofapplication icons (e.g., 612A-612Z) (e.g., the predefined regioncorresponding to the modified first plurality of application icons isadjacent to the predefined region (e.g., 628) corresponding to the firstset of one or more user interface elements (e.g., 622A)), the electronicdevice replaces display of the modified first plurality of applicationicons (e.g., 612A-612Z) with display of the second plurality ofapplication icons (e.g., 612AA-612AK), wherein the predefined region(e.g., 630) corresponding to the modified first plurality of applicationicons does not overlap with the predefined region (e.g., 628)corresponding to the first set of one or more user interface elements(e.g., 622A). Replacing display of the modified first plurality ofapplication icons (e.g., 612A-612Z) includes ceasing display of themodified first plurality of application icons.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources for display inwidgets. The present disclosure contemplates that in some instances,this gathered data may include personal information data that uniquelyidentifies or can be used to contact or locate a specific person. Suchpersonal information data can include demographic data, location-baseddata, telephone numbers, email addresses, twitter IDs, home addresses,data or records relating to a user's health or level of fitness (e.g.,vital signs measurements, medication information, exercise information),date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toprovide useful, glanceable information in widgets. Further, other usesfor personal information data that benefit the user are alsocontemplated by the present disclosure. For instance, health and fitnessdata may be used to provide insights into a user's general wellness, ormay be used as positive feedback to individuals using technology topursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof displaying personal information data in widgets, the presenttechnology can be configured to allow users to select to “opt in” or“opt out” of participation in the collection of personal informationdata during registration for services or anytime thereafter. In additionto providing “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deletinsg data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, widgets canshow glanceable information from applications based on non-personalinformation data or a bare minimum amount of personal information.

1. (canceled)
 2. An electronic device, comprising: a display device; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors, the one or more programsincluding instructions for: concurrently displaying, via the displaydevice, a wake screen of the electronic device that includes one or morenotifications and a first set of one or more user interface elements;while concurrently displaying the wake screen and the first set of oneor more user interface elements, detecting a first user input; and inresponse to detecting the first user input: in accordance with adetermination that the first user input includes movement in a firstdirection, ceasing to display the first set of one or more userinterface elements and displaying the one or more notifications; and inaccordance with a determination that the first user input includesselection of a user interface element of the first set of one or moreuser interface elements and the electronic device is in an unlockedstate, displaying an application user interface corresponding to theselected user interface element.
 3. The electronic device of claim 1,the one or more programs further including instructions for: in responseto detecting the first user input and in accordance with a determinationthat the first user input includes selection of a user interface elementof the first set of one or more user interface elements and theelectronic device is in a locked state, attempting to biometricallyauthenticate a user.
 4. The electronic device of claim 1, wherein thewake screen of the electronic device further includes a graphical stateindicator that indicates whether the electronic device is in a locked orunlocked state.
 5. The electronic device of claim 1, wherein themovement in the second direction includes movement away from a firstedge of the display device toward a second edge of the display device,wherein the first edge is parallel to the second edge of the displaydevice.
 6. The electronic device of claim 1, the one or more programsfurther including instructions for: while displaying, on the displaydevice, the one or more notifications, receiving a second user inputthat includes movement in a third direction; and in response toreceiving the second user input that includes movement in the thirddirection, displaying a home screen user interface.
 7. The electronicdevice of claim 1, the one or more programs further includinginstructions for: while displaying, on the display device, the one ormore notifications, receiving a second user input; and in response toreceiving the second user input: in accordance with a determination thatthe second user input includes movement in a third direction, initiatinga process for displaying a home screen user interface.
 8. The electronicdevice of claim 7, the one or more programs further includinginstructions for: in accordance with a determination that the seconduser input includes movement in a third direction and the device is in alocked state, attempting to biometrically authenticate the user.
 9. Anon-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: concurrently displaying, via the displaydevice, a wake screen of the electronic device that includes one or morenotifications and a first set of one or more user interface elements;while concurrently displaying the wake screen and the first set of oneor more user interface elements, detecting a first user input; and inresponse to detecting the first user input: in accordance with adetermination that the first user input includes movement in a firstdirection, ceasing to display the first set of one or more userinterface elements and displaying the one or more notifications; and inaccordance with a determination that the first user input includesselection of a user interface element of the first set of one or moreuser interface elements and the electronic device is in an unlockedstate, displaying an application user interface corresponding to theselected user interface element.
 10. A method, comprising: at anelectronic device with a display device: concurrently displaying, viathe display device, a wake screen of the electronic device that includesone or more notifications and a first set of one or more user interfaceelements; while concurrently displaying the wake screen and the firstset of one or more user interface elements, detecting a first userinput; and in response to detecting the first user input: in accordancewith a determination that the first user input includes movement in afirst direction, ceasing to display the first set of one or more userinterface elements and displaying the one or more notifications; and inaccordance with a determination that the first user input includesselection of a user interface element of the first set of one or moreuser interface elements and the electronic device is in an unlockedstate, displaying an application user interface corresponding to theselected user interface element.